|
Virtual Box memory low error
Discussions related to using VirtualBox on Windows hosts.
Post a reply
15 posts
• Page 1 of 1
Reply with quote
Virtual Box memory low error
 by Coder13 » 4. Jun 2016, 07:06
I wanted to create a Window XP virtual machine in my Window 10 computer but it keeps showing me a memory low error and I open task manager to check my computer memory and the memory is very low.My computer have like 3.8gb of memory and it using 3.0gb of my memory..Can you guys help me please....I'm having this trouble since I install window xp on VirtualBox again... T-T
Attachments
The Error
Untitled.png (78.59 KiB) Viewed 5141 times
Coder13
Posts: 3Joined: 4. Jun 2016, 06:54
Top
Reply with quote
Re: Virtual Box memory low error
by BillG » 4. Jun 2016, 07:17
You are starving the host by allocating too much memory to the vm. XP should run happily with 1G of memory. (Mine certainly does). Try allocating1G to the XP vm.
Bill
BillG
Volunteer
Posts: 5072Joined: 19. Sep 2009, 04:44Location: Sydney, Australia
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows 10,7 and earlier
Top
Reply with quote
Re: Virtual Box memory low error
by Coder13 » 4. Jun 2016, 07:26
I give the XP vm like 2048mb and it says that the host will low on memory if I do this....And my window 10 computer is really running low on memory(I think its RAM) what do I have to do?
Coder13
Posts: 3Joined: 4. Jun 2016, 06:54
Top
Reply with quote
Re: Virtual Box memory low error
by mpack » 4. Jun 2016, 09:56
Bill already told you: 1GB is plenty for an XP VM. In fact it will probably be happy with 512MB.If you need to continue this discussion then provide a VM log file: with the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.
mpack
Site Moderator
Posts: 38170Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP
Top
Reply with quote
Re: Virtual Box memory low error
by Coder13 » 4. Jun 2016, 10:36
Ok thnx for your reply:D
Coder13
Posts: 3Joined: 4. Jun 2016, 06:54
Top
Reply with quote
Re: Virtual Box memory low error
by Mahdi63 » 14. May 2017, 10:09
Would please at least give address of other related posts for me problem not solved guest: xp 32 host: win 10 64x
Mahdi63
Posts: 14Joined: 14. May 2017, 10:06
Top
Reply with quote
Re: Virtual Box memory low error
by socratis » 14. May 2017, 10:17
@Mahdi63There is nothing to solve. Give the WinXP guest 512 MB of RAM. Maximum 1 GB. If you do, what's the problem?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis
Site Moderator
Posts: 27689Joined: 22. Oct 2010, 11:03Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Top
Reply with quote
Re: Virtual Box memory low error
by Mahdi63 » 2. Jun 2017, 20:48
I have given it 512 mb but it does not go beyond 63mb. By the way, when guest os is slow, there is full hdd activity in virtualbox.exe so it is the process that show guest memory.
Mahdi63
Posts: 14Joined: 14. May 2017, 10:06
Top
Reply with quote
Re: Virtual Box memory low error
by erdeslawe » 2. Jun 2017, 21:04
The Windows Task Manager tells you how much memory is being used by each task. It does NOT tell you how much memory the system has available; and the Tasks only use the amount of memory they actually need. If all of the memory was being used all of the time, then the system would grind to a halt!
erdeslawe
Volunteer
Posts: 241Joined: 8. Jul 2015, 10:23
Top
Reply with quote
Re: Virtual Box memory low error
by Perryg » 2. Jun 2017, 21:40
Not to mention that the VBoxManager will never use any more than 63-64MB It is just the manager. The actual guest service is what you need to find. One of the VBoxSVC services when the guest is running.If you want to continue this topic you should at the very least post the guests log file ( as an attachment ) so we can see what the memory looks like to VirtualBox.
Perryg
Site Moderator
Posts: 34373Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX
Top
Reply with quote
Re: Virtual Box memory low error
by Mahdi63 » 2. Jun 2017, 23:39
Attached
Attachments
 SAFE X-2017-06-03-02-04-02.log
(106.83 KiB) Downloaded 12 times
Mahdi63
Posts: 14Joined: 14. May 2017, 10:06
Top
Reply with quote
Re: Virtual Box memory low error
by Perryg » 3. Jun 2017, 00:18
Start with looking what was available to the guest on boot time. 2.2GB which means you are probably running a lot on the host and you need to make sure not to just leave unused programs running. Web browser with tabs are the worst user of memory and depending on how many tabs you have open you don't leave a lot for the host and guest to operate at the same time.Code: Select all Expand viewCollapse view00:00:06.193785 Host RAM: 8075MB (7.8GB) total, 2290MB (2.2GB) availableThese entries show you have an issue with something called filesyncshell. This can cause issues and you need to figure out how to handle it. I will leave this to someone that actually deals with Windows.Code: Select all Expand viewCollapse view00:14:08.727843 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_SUP_VP_NOT_OWNED_BY_TRUSTED_INSTALLER fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume3\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll: supHardenedWinVerifyImageByHandle: TrustedInstaller is not the owner of '\Device\HarddiskVolume3\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll'.00:14:08.749344 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll' (C:\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll): rcNt=0xc000019000:14:08.750414 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_SUP_VP_NOT_OWNED_BY_TRUSTED_INSTALLER fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume3\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll00:14:08.750520 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll' (C:\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll): rcNt=0xc000019000:14:08.751517 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_SUP_VP_NOT_OWNED_BY_TRUSTED_INSTALLER fImage=1 fProtect=0x0 fAccess=0x0 cHits=2 \Device\HarddiskVolume3\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll00:14:08.751620 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll' (C:\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll): rcNt=0xc000019000:14:08.752536 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_SUP_VP_NOT_OWNED_BY_TRUSTED_INSTALLER fImage=1 fProtect=0x0 fAccess=0x0 cHits=3 \Device\HarddiskVolume3\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll00:14:08.752663 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll' (C:\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll): rcNt=0xc000019000:14:08.753597 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_SUP_VP_NOT_OWNED_BY_TRUSTED_INSTALLER fImage=1 fProtect=0x0 fAccess=0x0 cHits=4 \Device\HarddiskVolume3\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll00:14:08.753736 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll' (C:\Users\Mahdi\AppData\Local\Microsoft\OneDrive\17.3.6799.0327_1\amd64\FileSyncShell64.dll): rcNt=0xc0000190Now we see the guest has been running for 52+ hours and at least this log does not show a low memory error so if you saw one during this run the host is where you must deal with this.Code: Select all Expand viewCollapse view52:35:22.218618 GUI: UIMediumEnumerator: Medium-enumeration finished!At this point I don't see anything that would indicate a VirtualBox issue and it is more than likely just an issue with memory usage and the lack of available memory for the host. I was going to tell you to use a special command to force VirtualBox to reserve the memory that the guest is using, but that would probably cause you as many if not more problems in your case.
Perryg
Site Moderator
Posts: 34373Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX
Top
Reply with quote
Re: Virtual Box memory low error
by Mahdi63 » 3. Jun 2017, 02:56
It never give an error, it becomes so slow. As you can see still a lot of free memory on host and vboxsvr is using 2 mb
Mahdi63
Posts: 14Joined: 14. May 2017, 10:06
Top
Reply with quote
Re: Virtual Box memory low error
by Perryg » 3. Jun 2017, 03:09
Where is the evidence of the "lot of free memory" and the "vboxsvr using 2mb"? Have I missed something, because I don't see it.
Perryg
Site Moderator
Posts: 34373Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX
Top
Reply with quote
Re: Virtual Box memory low error
by socratis » 3. Jun 2017, 06:56
Mahdi63 wrote:It never give an error, it becomes so slow.From a Microsoft article, RAM, virtual memory, pagefile, and memory management in Windows:On any computer system, as the load increases (the number of users, the volume of work), performance decreases, but in a nonlinear manner. Any increase in load or demand, beyond a certain point, causes a significant decrease in performance. This means that some resource is in critically short supply and has become a bottleneck.Please read the whole thing.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis
Site Moderator
Posts: 27689Joined: 22. Oct 2010, 11:03Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Top
Post a reply
15 posts
• Page 1 of 1
Return to VirtualBox on Windows Hosts
Who is online
Users browsing this forum: No registered users and 27 guests
|